docs: blog post on read-cache-after-write consistency#3194
Merged
Conversation
openshift-ci
bot
added
the
do-not-merge/work-in-progress
csviri
changed the title
openshift-merge-robot
added
the
needs-rebase
csviri
force-pushed
the
blog-read-after-write
branch
from
4ee62d8 to
d1d0133
Compare
openshift-merge-robot
removed
the
needs-rebase
csviri
force-pushed
the
blog-read-after-write
branch
from
0ea2ba4 to
16ea561
Compare
openshift-merge-robot
added
the
needs-rebase
csviri
force-pushed
the
blog-read-after-write
branch
from
ebcf9bc to
10ccea7
Compare
openshift-merge-robot
removed
the
needs-rebase
csviri
changed the title
openshift-ci
bot
removed
the
do-not-merge/work-in-progress
Contributor
There was a problem hiding this comment.
Pull request overview
Adds documentation content describing the new read-cache-after-write consistency feature and links it from existing release/blog pages; also adjusts an SSA patching integration test reconciler to use reschedule() behavior.
Changes:
- Add a new blog post explaining read-cache-after-write consistency and event filtering.
- Update the v5.3 release post and a deprecated blog post to link to the new blog post.
- Modify
PatchResourceWithSSAReconcilerto reschedule reconciliation (test behavior).
Reviewed changes
Copilot reviewed 4 out of 4 changed files in this pull request and generated 7 comments.
| File | Description |
|---|---|
| operator-framework/src/test/java/io/javaoperatorsdk/operator/baseapi/patchresourcewithssa/PatchResourceWithSSAReconciler.java | Changes how the test reconciler schedules the “next pass” reconciliation. |
| docs/content/en/blog/releases/v5-3-release.md | Adds a link to the new read-after-write consistency blog post from the 5.3 release notes. |
| docs/content/en/blog/news/read-after-write-consistency.md | New blog post describing the read-cache-after-write consistency feature and rationale. |
| docs/content/en/blog/news/primary-cache-for-next-recon.md | Updates deprecated post to reference the new docs/blog content for the replacement feature. |
You can also share your feedback on Copilot code review. Take the survey.
| res.getSpec().setControllerManagedValue(ADDED_VALUE); | ||
| // test assumes we will run this in the next reconciliation | ||
| return UpdateControl.patchResource(res).reschedule(); | ||
| return UpdateControl.<PatchResourceWithSSACustomResource>noUpdate().reschedule(); |
Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
Collaborator
Author
Contributor
There was a problem hiding this comment.
Pull request overview
Adds a new documentation blog post explaining the new read-cache-after-write consistency guarantees introduced in v5.3.0, and links to it from existing release/news content so readers can find the deeper rationale and details.
Changes:
- Link the v5.3 release notes to a new “read-after-write consistency” blog post.
- Add a new blog post describing the problem space, algorithm, and event filtering behavior.
- Update the older “primary cache for next reconciliation” post to point readers to the new docs + blog post.
Reviewed changes
Copilot reviewed 3 out of 3 changed files in this pull request and generated 3 comments.
| File | Description |
|---|---|
| docs/content/en/blog/releases/v5-3-release.md | Adds a link from release notes to the new blog post. |
| docs/content/en/blog/news/read-after-write-consistency.md | New long-form post describing read-cache-after-write consistency + event filtering. |
| docs/content/en/blog/news/primary-cache-for-next-recon.md | Updates deprecation note to reference the new docs/blog post. |
You can also share your feedback on Copilot code review. Take the survey.
Comment on lines
+13
to
+14
| is not required anymore. See the [docs](./../../docs/documentation/reconciler.md#read-cache-after-write-consistency-and-event-filtering) and | ||
| related [blog post](read-after-write-consistency.md) for details. |
|
|
||
| Having the TRC has an additional advantage: since we have the resource instantly in our caches, we can | ||
| elegantly continue the reconciliation in the same pass and reconcile resources that depend | ||
| on the latest state. More concretely, this also helps with our [Dependent Resources / Workflows](../../docs/documentation/dependent-resource-and-workflows/workflows.md#reconcile-sample) |
Comment on lines
+13
to
+14
| is not required anymore. See the [docs](./../../docs/documentation/reconciler.md#read-cache-after-write-consistency-and-event-filtering) and | ||
| related [blog post](read-after-write-consistency.md) for details. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Signed-off-by: Attila Mészáros a_meszaros@apple.com